Skip to content

Conversation

andyleejordan
Copy link
Member

Coupled with a change to PSES, this enables us to workaround VS Code's
API limitations where our interactive "get user's arguments" command can
only return a string, not an array of strings, which is then passed as a
single argument to PSES. Because it likely contains spaces (and multiple
arguments), we need to instruct PSES to not quote the string in this
special case. It would be easier if we could just pass a list of string
arguments, but so it goes.

Coupled with PowerShell/PowerShellEditorServices#1702, this fixes #3770.

Coupled with a change to PSES, this enables us to workaround VS Code's
API limitations where our interactive "get user's arguments" command can
only return a string, not an array of strings, which is then passed as a
single argument to PSES. Because it likely contains spaces (and multiple
arguments), we need to instruct PSES to not quote the string in this
special case. It would be easier if we could just pass a list of string
arguments, but so it goes.
@andyleejordan
Copy link
Member Author

We're going to fix this by reverting the argument escaping.

@andyleejordan andyleejordan deleted the andschwa/untitled-with-args branch June 24, 2022 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using a launch configuration with interactive arguments does not work correctly in Powershell preview extension
1 participant